Dubbo client can not supported string message |
您所在的位置：网站首页 › dubbo client can not supported string message › Dubbo client can not supported string message |
|
pregunta
De repente lanzar las anormalidades a continuación en línea 2019-09-26 15:35:22,325 ERROR [DubboClientHandler-ip2:15196-thread-2] c.a.d.r.e.s.h.HeaderExchangeHandler:: {} [DUBBO] Dubbo client can not supported string message: in channel: NettyChannel [channel=[id: 0x5210fa0a, /ip1:43814 => /ip2:15196]], url: dubbo://ip2:15196/com.....alge.eta.service.EtaService?accesslog=false&anyhost=true&application=system-dispatch&check=false&codec=dubbo&default.executes=100&default.loadbalance=roundrobin&dubbo=2.5.3&heartbeat=60000&interface=com.....alge.eta.service.EtaService&logger=slf4j&methods=getModelResult,getXingTangModelResult&pid=1&retries=0&side=consumer&timeout=400×tamp=1568871901241, dubbo version: 2.5.3, current host: ip1 java.lang.Exception: Dubbo client can not supported string message: in channel: NettyChannel [channel=[id: 0x5210fa0a, /ip1:43814 => /ip2:15196]], url: dubbo://ip2:15196/com.....alge.eta.service.EtaService?accesslog=false&anyhost=true&application=system-dispatch&check=false&codec=dubbo&default.executes=100&default.loadbalance=roundrobin&dubbo=2.5.3&heartbeat=60000&interface=com.....alge.eta.service.EtaService&logger=slf4j&methods=getModelResult,getXingTangModelResult&pid=1&retries=0&side=consumer&timeout=400×tamp=1568871901241 at com.alibaba.dubbo.remoting.exchange.support.header.HeaderExchangeHandler.received(HeaderExchangeHandler.java:180) ~[dubbo-2.5.3.jar!/:2.5.3] at com.alibaba.dubbo.remoting.transport.DecodeHandler.received(DecodeHandler.java:52) ~[dubbo-2.5.3.jar!/:2.5.3] at com.alibaba.dubbo.remoting.transport.dispatcher.ChannelEventRunnable.run(ChannelEventRunnable.java:82) ~[dubbo-2.5.3.jar!/:2.5.3] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_201] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_201] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_201]Esto es un poco menos, por lo que podemos encontrar más información sobre la expectativa del registro de la aplicación. ¿En qué pistas se basan? Online Trace_ID no se imprime, por lo que solo puede verlo de acuerdo con el registro de subprocesos, es decir,: DubBoclientHandler-IP2-Thread-2. Entonces encontré los registros anormales a continuación 2019-09-26 15:35:22,310 WARN [DubboClientHandler-ip2:15196-thread-2] c.a.d.r.e.s.DefaultFuture:: {} [DUBBO] The timeout response finally returned at 2019-09-26 15:35:22.310, response Response [id=1254844, version=null, status=50, event=false, error=Failed to send response: Response [id=1254844, version=2.0.0, status=20, event=false, error=null, result=RpcResult [result=[com.....alge.eta.dto.ResultRiderDTO@17bdd760, com.....alge.eta.dto.ResultRiderDTO@198283d3, com.....alge.eta.dto.ResultRiderDTO@323b5e16, com.....alge.eta.dto.ResultRiderDTO@66d2204d, com.....alge.eta.dto.ResultRiderDTO@43fc4bb6, com.....alge.eta.dto.ResultRiderDTO@3b1ffa8c, com.....alge.eta.dto.ResultRiderDTO@241b5a75, com.....alge.eta.dto.ResultRiderDTO@59b14bb], exception=null]], cause: java.util.ConcurrentModificationException java.util.ConcurrentModificationException at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:909) at java.util.ArrayList$Itr.next(ArrayList.java:859) at com.alibaba.com.caucho.hessian.io.CollectionSerializer.writeObject(CollectionSerializer.java:100) at com.alibaba.com.caucho.hessian.io.Hessian2Output.writeObject(Hessian2Output.java:408) at com.alibaba.com.caucho.hessian.io.JavaSerializer.writeObject(JavaSerializer.java:203) at com.alibaba.com.caucho.hessian.io.Hessian2Output.writeObject(Hessian2Output.java:408) at com.alibaba.dubbo.common.serialize.support.hessian.Hessian2ObjectOutput.writeObject(Hessian2ObjectOutput.java:92) at com.alibaba.dubbo.rpc.protocol.dubbo.DubboCodec.encodeResponseData(DubboCodec.java:200) at com.alibaba.dubbo.remoting.exchange.codec.ExchangeCodec.encodeResponse(ExchangeCodec.java:276) at com.alibaba.dubbo.remoting.exchange.codec.ExchangeCodec.encode(ExchangeCodec.java:77) at com.alibaba.dubbo.rpc.protocol.dubbo.DubboCountCodec.encode(DubboCountCodec.java:39) at com.alibaba.dubbo.remoting.transport.netty.NettyCodecAdapter$InternalEncoder.encode(NettyCodecAdapter.java:81) at org.jboss.netty.handler.codec.oneone.OneToOneEncoder.handleDownstream(OneToOneEncoder.java:66) at org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:591) at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendDownstream(DefaultChannelPipeline.java:776) at org.jboss.netty.channel.SimpleChannelHandler.writeRequested(SimpleChannelHandler.java:304) at com.alibaba.dubbo.remoting.transport.netty.NettyHandler.writeRequested(NettyHandler.java:99) at org.jboss.netty.channel.SimpleChannelHandler.handleDownstream(SimpleChannelHandler.java:266) at org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:591) at org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:582) at org.jboss.netty.channel.Channels.write(Channels.java:611) at org.jboss.netty.channel.Channels.write(Channels.java:578) at org.jboss.netty.channel.AbstractChannel.write(AbstractChannel.java:251) at com.alibaba.dubbo.remoting.transport.netty.NettyChannel.send(NettyChannel.java:98) at com.alibaba.dubbo.remoting.transport.AbstractPeer.send(AbstractPeer.java:51) at com.alibaba.dubbo.remoting.exchange.support.header.HeaderExchangeHandler.received(HeaderExchangeHandler.java:171) at com.alibaba.dubbo.remoting.transport.DecodeHandler.received(DecodeHandler.java:52) at com.alibaba.dubbo.remoting.transport.dispatcher.ChannelEventRunnable.run(ChannelEventRunnable.java:82) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) , result=null], channel: /ip1:43814 -> /ip2:15196, dubbo version: 2.5.3, current host: ip1El problema ha sido claro y la información anormal se proporciona al proveedor de interfaz. Encuentre la ID de solicitud de solicitud (1254844) de acuerdo con la ID de respuesta de respuesta (1254844), encuentre el posicionamiento de registro comercial correspondiente al trazo_id (ID de pedido) del problema, y de acuerdo con el posicionamiento de ID de pedido para el punto de influencia comercial para confirmar el punto rango de influencia 2019-09-26 15:35:21,645 ERROR [immediately-dispatch-44] c.d.d.f.r.r.i.OrderSendTimeOutFilter:getModelResult:287 {orderId=483047323593828352} Llame a la anormalidad del modelo de predicción del tiempo de entrega, etaservice#getModelResult com.alibaba.dubbo.rpc.RpcException: Failed to invoke the method getXingTangModelResult in the service com.....alge.eta.service.EtaService. Tried 1 times of the providers [ip2:15196] (1/2) from the registry 172.24.0.6:2186 on the consumer ip1 using the dubbo version 2.5.3. Last error is: Invoke remote method timeout. method: getXingTangModelResult, provider: dubbo://ip2:15196/com.....alge.eta.service.EtaService?accesslog=false&anyhost=true&application=system-dispatch&check=false&default.executes=100&default.loadbalance=roundrobin&dubbo=2.5.3&interface=com.....alge.eta.service.EtaService&logger=slf4j&methods=getModelResult,getXingTangModelResult&pid=1&retries=0&side=consumer&timeout=400×tamp=1568871901241, cause: Waiting server-side response timeout. start time: 2019-09-26 15:35:21.244, end time: 2019-09-26 15:35:21.645, client elapsed: 0 ms, server elapsed: 401 ms, timeout: 400 ms, request: Request [id=1254844, version=2.0.0, twoway=true, event=false, broken=false, data=RpcInvocation [methodName=getXingTangModelResult, parameterTypes=[interface java.util.List], arguments=[[com.....alge.eta.dto.EtaRiderDTO@7de6164, com.....alge.eta.dto.EtaRiderDTO@44ac0621, com.....alge.eta.dto.EtaRiderDTO@60af7dfc, com.....alge.eta.dto.EtaRiderDTO@3940bef0, com.....alge.eta.dto.EtaRiderDTO@2bfb5818, com.....alge.eta.dto.EtaRiderDTO@380cd692, com.....alge.eta.dto.EtaRiderDTO@2ce11da9, com.....alge.eta.dto.EtaRiderDTO@37614eb1, com.....alge.eta.dto.EtaRiderDTO@7b618db0, com.....alge.eta.dto.EtaRiderDTO@2116bec, com.....alge.eta.dto.EtaRiderDTO@27733f2, com.....alge.eta.dto.EtaRiderDTO@1ed63260, com.....alge.eta.dto.EtaRiderDTO@593b5139, com.....alge.eta.dto.EtaRiderDTO@47a389e5, com.....alge.eta.dto.EtaRiderDTO@81e1, com.....alge.eta.dto.EtaRiderDTO@7dfd635c, com.....alge.eta.dto.EtaRiderDTO@669f1bed, com.....alge.eta.dto.EtaRiderDTO@7e872fed]], attachments={path=com.....alge.eta.service.EtaService, interface=com.....alge.eta.service.EtaService, version=0.0.0, timeout=400}]], channel: /ip1:43814 -> /ip2:15196 at com.alibaba.dubbo.rpc.cluster.support.FailoverClusterInvoker.doInvoke(FailoverClusterInvoker.java:101) ~[dubbo-2.5.3.jar!/:2.5.3] at com.alibaba.dubbo.rpc.cluster.support.AbstractClusterInvoker.invoke(AbstractClusterInvoker.java:227) ~[dubbo-2.5.3.jar!/:2.5.3] at com.alibaba.dubbo.rpc.cluster.support.wrapper.MockClusterInvoker.invoke(MockClusterInvoker.java:72) ~[dubbo-2.5.3.jar!/:2.5.3] at com.alibaba.dubbo.rpc.cluster.support.AvailableCluster$1.doInvoke(AvailableCluster.java:43) ~[dubbo-2.5.3.jar!/:2.5.3] at com.alibaba.dubbo.rpc.cluster.support.AbstractClusterInvoker.invoke(AbstractClusterInvoker.java:227) ~[dubbo-2.5.3.jar!/:2.5.3] at com.alibaba.dubbo.rpc.cluster.support.wrapper.MockClusterInvoker.invoke(MockClusterInvoker.java:72) ~[dubbo-2.5.3.jar!/:2.5.3] at com.alibaba.dubbo.rpc.proxy.InvokerInvocationHandler.invoke(InvokerInvocationHandler.java:52) ~[dubbo-2.5.3.jar!/:2.5.3] at com.alibaba.dubbo.common.bytecode.proxy18.getXingTangModelResult(proxy18.java) ~[?:2.5.3] at com.....dispatch.filter.rules.riderfilter.impl.OrderSendTimeOutFilter.getModelResult(OrderSendTimeOutFilter.java:281) ~[dispatch-filter-rules-1.72.0.jar!/:1.72.0] at com.....dispatch.filter.rules.riderfilter.impl.OrderSendTimeOutFilter.beforeFilter(OrderSendTimeOutFilter.java:101) ~[dispatch-filter-rules-1.72.0.jar!/:1.72.0] at com.....dispatch.filter.rules.riderfilter.AbstractRiderFilter.filter(AbstractRiderFilter.java:34) ~[dispatch-filter-rules-1.72.0.jar!/:1.72.0] at com.....dispatch.struct.dispatcher.AbstractSingleDispatcher.filterInner(AbstractSingleDispatcher.java:93) ~[dispatch-struct-1.0-SNAPSHOT.jar!/:1.0-SNAPSHOT] at com.....dispatch.struct.dispatcher.AbstractSingleDispatcher.filterRiders(AbstractSingleDispatcher.java:87) ~[dispatch-struct-1.0-SNAPSHOT.jar!/:1.0-SNAPSHOT] at com.....dispatch.dispatch.SystemSingleDispatcher.filterRiders(SystemSingleDispatcher.java:382) ~[system-dispatch-impl-0.0.1-SNAPSHOT.jar!/:0.0.1-SNAPSHOT] at com.....dispatch.struct.dispatcher.ConfigurableAbstractSingleAsyncDispatcher.dispatch(ConfigurableAbstractSingleAsyncDispatcher.java:33) ~[dispatch-struct-1.0-SNAPSHOT.jar!/:1.0-SNAPSHOT] at com.....dispatch.provider.SystemDispatchProviderImpl.startDispatch(SystemDispatchProviderImpl.java:112) ~[system-dispatch-impl-0.0.1-SNAPSHOT.jar!/:0.0.1-SNAPSHOT] at com.....dispatch.provider.SystemDispatchProviderImpl.lambda$null$0(SystemDispatchProviderImpl.java:65) ~[system-dispatch-impl-0.0.1-SNAPSHOT.jar!/:0.0.1-SNAPSHOT] at com.....wireless.threadpool.MonitoringTask.run(MonitoringTask.java:50) ~[wireless-threadpool-0.0.1-SNAPSHOT.jar!/:0.0.1-SNAPSHOT] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_201] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_201] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_201] Caused by: com.alibaba.dubbo.remoting.TimeoutException: Waiting server-side response timeout. start time: 2019-09-26 15:35:21.244, end time: 2019-09-26 15:35:21.645, client elapsed: 0 ms, server elapsed: 401 ms, timeout: 400 ms, request: Request [id=1254844, version=2.0.0, twoway=true, event=false, broken=false, data=RpcInvocation [methodName=getXingTangModelResult, parameterTypes=[interface java.util.List], arguments=[[com.....alge.eta.dto.EtaRiderDTO@7de6164, com.....alge.eta.dto.EtaRiderDTO@44ac0621, com.....alge.eta.dto.EtaRiderDTO@60af7dfc, com.....alge.eta.dto.EtaRiderDTO@3940bef0, com.....alge.eta.dto.EtaRiderDTO@2bfb5818, com.....alge.eta.dto.EtaRiderDTO@380cd692, com.....alge.eta.dto.EtaRiderDTO@2ce11da9, com.....alge.eta.dto.EtaRiderDTO@37614eb1, com.....alge.eta.dto.EtaRiderDTO@7b618db0, com.....alge.eta.dto.EtaRiderDTO@2116bec, com.....alge.eta.dto.EtaRiderDTO@27733f2, com.....alge.eta.dto.EtaRiderDTO@1ed63260, com.....alge.eta.dto.EtaRiderDTO@593b5139, com.....alge.eta.dto.EtaRiderDTO@47a389e5, com.....alge.eta.dto.EtaRiderDTO@81e1, com.....alge.eta.dto.EtaRiderDTO@7dfd635c, com.....alge.eta.dto.EtaRiderDTO@669f1bed, com.....alge.eta.dto.EtaRiderDTO@7e872fed]], attachments={path=com.....alge.eta.service.EtaService, interface=com.....alge.eta.service.EtaService, version=0.0.0, timeout=400}]], channel: /ip1:43814 -> /ip2:15196 at com.alibaba.dubbo.remoting.exchange.support.DefaultFuture.get(DefaultFuture.java:107) ~[dubbo-2.5.3.jar!/:2.5.3] at com.alibaba.dubbo.remoting.exchange.support.DefaultFuture.get(DefaultFuture.java:84) ~[dubbo-2.5.3.jar!/:2.5.3] at com.alibaba.dubbo.rpc.protocol.dubbo.DubboInvoker.doInvoke(DubboInvoker.java:96) ~[dubbo-2.5.3.jar!/:2.5.3] at com.alibaba.dubbo.rpc.protocol.AbstractInvoker.invoke(AbstractInvoker.java:144) ~[dubbo-2.5.3.jar!/:2.5.3] at com.alibaba.dubbo.rpc.listener.ListenerInvokerWrapper.invoke(ListenerInvokerWrapper.java:74) ~[dubbo-2.5.3.jar!/:2.5.3] at com.alibaba.dubbo.monitor.support.MonitorFilter.invoke(MonitorFilter.java:75) ~[dubbo-2.5.3.jar!/:2.5.3] at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:91) ~[dubbo-2.5.3.jar!/:2.5.3] at com.....wireless.dubbo.filter.InvokeResultLogFilter.invoke(InvokeResultLogFilter.java:36) ~[dubbo-integration-0.0.1-SNAPSHOT.jar!/:0.0.1-SNAPSHOT] at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:91) ~[dubbo-2.5.3.jar!/:2.5.3] at com.alibaba.dubbo.rpc.protocol.dubbo.filter.FutureFilter.invoke(FutureFilter.java:53) ~[dubbo-2.5.3.jar!/:2.5.3] at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:91) ~[dubbo-2.5.3.jar!/:2.5.3] at com.alibaba.dubbo.rpc.filter.ConsumerContextFilter.invoke(ConsumerContextFilter.java:48) ~[dubbo-2.5.3.jar!/:2.5.3] at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:91) ~[dubbo-2.5.3.jar!/:2.5.3] at com.alibaba.dubbo.rpc.protocol.InvokerWrapper.invoke(InvokerWrapper.java:53) ~[dubbo-2.5.3.jar!/:2.5.3] at com.alibaba.dubbo.rpc.cluster.support.FailoverClusterInvoker.doInvoke(FailoverClusterInvoker.java:77) ~[dubbo-2.5.3.jar!/:2.5.3] ... 20 more Conclusión de problemas El inicio de sesión del cliente en el hilo Dubbo es adoptado de manera uniforme por el mango del cliente+Servidor IP: Port+ID de subproceso (por ejemplo, en el caso: DubBoclientHandler-IP2: 15196-Thread-2). De acuerdo con este formato, puede localizar el registro de comunicación en el mismo lado del servidor con el mismo lado del servidor. Asistir en problemas de posicionamiento del cliente La solicitud y la respuesta de Dubbo también coinciden con la ID que se puede rastrear, como la ID de solicitud y la ID de respuesta en el caso (1254844) (1254844) |
| CopyRight 2018-2019 办公设备维修网 版权所有 豫ICP备15022753号-3 |